Skip to content

Conversation

@ricardozanini
Copy link
Member

Fix #1185

Many thanks for submitting your Pull Request ❤️!

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@ricardozanini ricardozanini requested a review from a team as a code owner June 13, 2025 22:57
@ricardozanini ricardozanini added area:client This item is related to the client extension backport-main-lts labels Jun 13, 2025
@ricardozanini
Copy link
Member Author

@edeandrea, mind taking a look on your side? We set additionalProperties: true on the schema if it's an object type without properties, and a default value is specified.

That won't fix the model, though. You may notice inconsistencies in your API. The ideal solution is to resolve the issue on the server side.

[.description]
--
Path to the Moqu (relative to the project).
Path to the Moqu OpenAPI files, relative to the `src/main/resources` directory.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mcruzdev when sending PRs to server/moqu make sure to run the whole build, from the top, locally.

…default value and no props

Signed-off-by: Ricardo Zanini <[email protected]>
Signed-off-by: Ricardo Zanini <[email protected]>
Copy link
Contributor

@gmunozfe gmunozfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a minor comment, good work @ricardozanini !

Co-authored-by: Gonzalo Muñoz <[email protected]>
@ricardozanini ricardozanini merged commit 328757a into quarkiverse:main Jun 16, 2025
11 checks passed
@ricardozanini ricardozanini deleted the issue-1185 branch June 16, 2025 18:33
github-actions bot pushed a commit that referenced this pull request Jun 16, 2025
…ue and no props (#1193)

* Fix #1185 - Add additionalProperties when type object has default value and no props

Signed-off-by: Ricardo Zanini <[email protected]>

* Fix Windows path

Signed-off-by: Ricardo Zanini <[email protected]>

* Adding Gonzalo's comment

Co-authored-by: Gonzalo Muñoz <[email protected]>

---------

Signed-off-by: Ricardo Zanini <[email protected]>
Co-authored-by: Gonzalo Muñoz <[email protected]>
ricardozanini added a commit that referenced this pull request Jun 16, 2025
…ue and no props (#1193) (#1199)

* Fix #1185 - Add additionalProperties when type object has default value and no props



* Fix Windows path



* Adding Gonzalo's comment



---------

Signed-off-by: Ricardo Zanini <[email protected]>
Co-authored-by: Ricardo Zanini <[email protected]>
Co-authored-by: Gonzalo Muñoz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:client This item is related to the client extension backport-main-lts

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Generating model with property of object type doesn't seem to work

4 participants